Broadband telecommunications system

ABSTRACT

A method of operating a communication signaling processor is disclosed. The method comprises receiving a signaling message for a voice call to a called party, processing the signaling message to transfer a query to a database that is updated when the called party changes locations, receiving a response from the database, and processing the response to select an identifier for a header of a voice communication to route the voice call to the called party.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of U.S. patent applicationSer. No. 10/686,916, filed Oct. 16, 2003; which is a continuation ofU.S. Pat. No. 6,665,294, filed Aug. 5, 2002; which is a continuation ofU.S. Pat. No. 6,452,928, filed Nov. 12, 1999; which is a continuation ofU.S. Pat. No. 5,991,301, filed on Sep. 8, 1995, and which is herebyincorporated by reference into this application.

BACKGROUND

At present, Asynchronous Transfer Mode (ATM) technology is beingdeveloped to provide broadband switching capability. Some ATM systemshave used ATM cross-connects to provide virtual connections.Cross-connect devices do not have the capacity to process signaling.Signaling refers to messages that are used by telecommunicationsnetworks to set-up and tear down calls. Thus, ATM cross-connects cannotmake connections on a call by call basis. As a result, connectionsthrough cross-connect systems must be pre-provisioned. They provide arelatively rigid switching fabric. Due to this limitation, ATMcross-connect systems have been primarily used to provide dedicatedconnections, such as permanent virtual circuits (PVCs) and permanentvirtual paths (PVPs). But, they do not to provide ATM switching on acall by call basis as required to provide switched virtual circuits(SVCs) or switched virtual paths (SVPs). Those skilled in the art arewell aware of the efficiencies created by using SVPs and SVCs as opposedto PVCs and PVPs. SVCs and SVPs utilize bandwidth more efficiently.

ATM switches have also been used to provide PVCs and PVPs. Since PVCsand PVPs are not established on a call-by-call basis, the ATM switchdoes need to use its call processing or signaling capacity. ATM switchesrequire both signaling capability and call processing capability toprovide SVCs and SVPs. In order to achieve virtual connection switchingon a call by call basis, ATM switches are being developed that canprocess calls in response to signaling to provide virtual connectionsfor each call. These systems cause problems because they must be verysophisticated to support current networks. These ATM switches mustprocess high volumes of calls and transition legacy services fromexisting networks. An example would be an ATM switch that can handlelarge numbers of POTS, 800, and VPN calls. This generation ofsophisticated ATM switches is not yet mature and should be expensivewhen they are first deployed.

Currently, ATM multiplexers are being developed that can interworktraffic into ATM cells and multiplex the cells for transport over an ATMnetwork. One example of an application of these muxes is provided by T1transport over an ATM connection. Traffic that leaves the switch in T1format is muxed into ATM cells for transport over a high speedconnection. Before the cells reach another switch, they are convertedback into the T1 format. Thus, the ATM mux is used for high speedtransport. The ATM mux is not used to select virtual connections on acall-by-call basis. Unfortunately, there is not a telecommunicationssystem that can provide ATM switching on a call by call basis withoutrelying on the call processing and signaling capability of an ATMswitch.

SUMMARY

A method of operating a communication signaling processor is disclosed.The method comprises receiving a signaling message for a voice call to acalled party, processing the signaling message to transfer a query to adatabase that is updated when the called party changes locations,receiving a response from the database, and processing the response toselect an identifier for a header of a voice communication to route thevoice call to the called party.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a version of the present invention.

FIG. 2 is a block diagram of a version of the present invention.

FIG. 3 is a block diagram of a version of the present invention.

FIG. 4 is a block diagram of a version of the present invention.

FIG. 5 is a block diagram of a version of the present invention.

FIG. 6 depicts a logic diagram of a version of the invention.

FIG. 7 depicts a logic diagram of a version of the invention.

FIG. 8 depicts a logic diagram of a version of the invention.

FIG. 9 depicts a logic diagram of a version of the invention.

FIG. 10 depicts a flow diagram of a version of the invention.

FIG. 11 depicts a flow diagram of a version of the invention.

FIG. 12 depicts a flow diagram of a version of the invention.

DETAILED DESCRIPTION

For purposes of clarity, the term “connection” will be used to refer tothe transmission media used to carry user traffic. The term “link” willbe used to refer to the transmission media used to carry signaling. Onthe Figures, connections are shown by a single line and signaling linksare shown by double lines.

FIG. 1 depicts a version of the present invention. Shown istelecommunications system 100, user 110, and user 120.Telecommunications system 100 includes ATM interworking multiplexer(mux) 130, mux 140, ATM cross-connect system 150, and signalingprocessing system 160. User 110 is connected to mux 130 by connection180. Mux 130 and mux 140 are connected through cross-connect system 150by connection 181. Mux 140 is connected to user 120 by connection 182.Signaling processing system 160 is linked to user 110 by link 190, tomux 130 by link 191, to mux 140 by link 192, and to user 120 by link193.

Those skilled in the art are aware that large networks have many morecomponents than are shown. For example, there would typically be amultitude of virtual connections through ATM cross-connect system 150.The number of these components has been restricted for clarity. Theinvention is fully applicable to a large network.

User 110 and user 120 could be any entity that suppliestelecommunications traffic to network 100. Some examples would be alocal exchange carrier (LEC) switch or customer premises equipment(CPE). Typically, the user traffic would be provided to system 100 inDS3, DS1, or OC-3 format that have embedded DS0 and VT 1.5 circuits.Connections 180 and 182 represent any connection that might be used byuser 120 to access system 100 and would also include formats such as E1,E3, and DS2. As such, these connections are periodically referred to asaccess connections. Connections 180 and 182 would typically be DS0connections embedded within a DS3 connection, however, the inventionfully contemplates other connection being used with a few examples beinga fractional DS1, a clear DS3, or even SONET OC-3. Links 190 and 193 areany links capable of transferring signaling messages with an examplebeing Signaling System #7 (SS7) links. ATM cross-connect system 150 isany system that provides a plurality of virtual connections. Such asystem could be comprised of individual ATM cross-connect devicesinterconnected by ATM connections using DS3 or SONET for transport. Anexample of an ATM cross-connect is the NEC Model 10. Connection 181could be any virtual connection. Typically, the virtual connection woulduse DS3 or SONET for transport. ATM cross-connect system 150 would bepre-provisioned to provide a plurality of virtual connections throughthe cross-connect system, and virtual connection 181 represents one ofthese connections. As virtual connections are logical paths, manyphysical paths can be used based on the pre-provisioning of ATMcross-connect system 150. Links 191 and 192 could be any links capableof transporting data messages. Examples of such links could be SS7 orUDP/IP. The components described in this paragraph are known in the art.

Signaling processing system 160 is any processing platform that canreceive and process signaling to select virtual connections, and thengenerate and transmit signaling to identify the selections. Variousforms of signaling are contemplated by the invention, including SS7, C7,and user to network interface (UNI) signaling. A preferred embodiment ofthe signaling processor is discussed in detail toward the end of thedisclosure.

Mux 130 could be any muxing system operable to place user informationarriving over connection 180 on the virtual connection selected bysignaling processing system 160. Typically, this involves receivingsignaling messages from signaling processing system 160 that identifyassignments of virtual connections to an access connection on a call bycall basis. The mux would convert user traffic from access connection180 into ATM cells that identify the selected virtual connection. Mux140 is similar to mux 130. A preferred embodiment of these muxes arealso discussed in detail below.

The system would operate as follows for a call from user 110 to user120. User 110 would send a signaling message over link 190 to system 100initiating the call. Signaling processing system 160 would process themessage. Such processing could include validation, screening,translating, route selection, echo control, network management,signaling, and billing. In particular, a virtual connection through ATMcross-connect system 150 from mux 130 to mux 140 would be selected, anda connection from mux 140 to user 120 would also be selected. Althoughmany possible connections would be available, only the selectedconnections are shown—connection 181 and connection 182. Generally, theselection is based on the dialed number, but call processing can entailmany other factors with a few examples being network loads and userrouting instructions. Signaling processing system 160 would then sendsignaling reflecting the selections to mux 130 and mux 140.

User 110 would also seize a connection to system 100. The connection isrepresented by connection 180 to mux 130. Although, only one connectionis shown for purposes of clarity, numerous connections would typicallybe available for seizure. The seized connection would be identified inthe signaling from user 110 to system 100. Signaling processing system160 would include the identity of this connection in its signal to mux130.

If required, user 120 would receive signaling to facilitate completionof the call. The signaling from signaling processing system 160 wouldindicate that system 100 was connecting to user 120 over connection 182.Typically, user 120 would accept and acknowledge the connection in asignaling message back to system 100.

Mux 130 would receive signaling from signaling processing system 160identifying connection 180 as the access connection and connection 181as the selected virtual connection through ATM cross-connect system 150.Mux 130 would convert the user information from connection 180 into ATMcells. Mux 130 would designate connection 181 in the cell headers.Connection 181 would have been previously provisioned through ATMcross-connect system 150 from mux 130 to mux 140.

Mux 140 would receive signaling from signaling processing system 160identifying connection 181 as the selected virtual connection andconnection 182 as the selected access connection to user 120. Mux 140would convert cells arriving on connection 181 to user informationsuitable for connection 182 to user 120. Although the above exampleemploys two muxes, a single mux could be employed for calls that enterand exit system 100 through the same mux. In this case, the ATM systemwould simply provide a virtual connection back to the same mux.

From the above discussion, it can be seen that multiple virtualconnections can be pre-provisioned through an ATM cross-connect systemto interconnect ATM interworking multiplexers. When a user places acall, one of the virtual connections is selected for the call by thesignal processing system and identified to the appropriate muxes. Themuxes convert the user information into cells that identify the selectedconnection. As such, user information can be switched through an ATMfabric on a call by call basis. The system does not require the callprocessing or signaling capabilities of an ATM switch (although an ATMswitch could be used to provide the virtual connections without usingits call processing and signaling functions). The system can alsoimplement enhanced services such as N00 and virtual private network(VPN).

FIG. 2 depicts another embodiment of the invention. In this embodiment,the user information from the access connection is capable of beingmuxed to the DS0 level, but this is not required in other embodiments.Additionally, SS7 signaling is used in this embodiment, but othersignaling protocols, such as C7 or UNI signaling, are also applicable tothe invention.

Shown are DS0 interface 210, ATM adaption layer (AAL) 220, ATM interface230, DS0—virtual connection assignment 240, call/connection manager(CCM) 250 and signal transfer point (STP) 260. Also shown areconnections 280-283 and links 290-292.

Connection 280 could by any connection or group of connections thatcontain information that can be converted to DS0 format. Examples ofthese connections are OC-3, VT1.5, DS3, and DS1. DS0 interface 210 isoperable to convert user information in these formats into the DS0format. AAL 220 comprises both a convergence sublayer and a segmentationand reassembly (SAR) layer. AAL 220 is operational to accept the userinformation in DS0 format from DS0 interface 210 and convert theinformation into ATM cells. AALs are known in the art and informationabout AALs is provided by International Telecommunications Union (ITU)document 1.363.1. An AAL for voice is also described in patentapplication Ser. No. 08/395,745, filed on Feb. 28, 1995, entitled “CellProcessing for Voice Transmission”, and hereby incorporated by referenceinto this application. ATM interface 230 is operational to accept ATMcells and transmit them over connection 283. Connection 283 is astandard DS3 or SONET connection transporting ATM cells. Connection 281is operational for the DS0 format and connection 282 is operational totransfer ATM cells.

It can be seen that a communications path through connections 280-283could be established to carry user information. Although thecommunications path has been described from connection 280 to connection283, the invention contemplates components that are also operational toperform reciprocal processing in the reverse direction. If thecommunications path is bi-directional, user information in ATM cellsarriving on connection 283 would be processed for output on connection280 in the appropriate format. Those skilled in the art will appreciatethat separate connections could also be set up in each direction, orthat only a connection in one direction may be required. Thesecomponents and their operation are known in the art.

Signaling links 290 and 291 are SS7 links. Link 292 is a data link withan example being an ethernet connection transporting UDP/IP. STP 260 isdevice that routes signaling messages. STPs are well known in the art.CCM 250 would be identified by its own signaling point code. STP 260would route signaling messages addressed to this point code to CCM 250.In some embodiments, STP 260 may also convert other point codes to thepoint code for CCM 250 so these signaling messages are also routed toCCM 250. Although point code conversion is not essential, it facilitatesthe transition of a network to the system of the invention. Theconversion could be implemented through a conversion table locatedbetween level 2 and level 3 of the message transfer part (MTP) functionof STP 260. The conversion table would convert the destination pointcode of the message to that of CCM 250, so that the route function ofMTP 3 would forward the message to CCM 250. Point code conversion couldbe based on many factors with a few examples being the destination pointcode, the origination point code, the signaling link, the circuitidentification code, the message type, and various combinations of theseand other factors. For example, SS7 Integrated Services User Part (ISUP)messages with particular OPC/DPC combinations could have the DPCconverted to the point code of CCM 250. These signaling messages wouldthen be routed to CCM 250 by STP 260. One version of a suitable STP isdisclosed in United States patent application entitled“Telecommunications Apparatus, System, and Method with Enhanced SignalTransfer Point”, filed simultaneously with this application, assigned tothe same entity, and hereby incorporated by reference into thisapplication.

CCM 250 is a signaling processor that operates as discussed above. Apreferred embodiment of CCM 250 is provided later. In this embodimentCCM 250 would be operable to receive and process SS7 signaling to selectconnections, and to generate and transmit signaling identifying theselections.

Assignment 240 is a control interface that accepts messages from CCM250. In particular, assignment 240 identifies DS0/virtual connectionassignments in the messages from link 292. These assignments areprovided to AAL 220 for implementation. As such, AAL 220 obtains thevirtual path identifier (VPI) and virtual channel identifier (VCI) foreach call from assignment 240. AAL 220 also obtains the identity of theDS0 for each call (or the DS0s for an Nx64 call). AAL 220 then convertsuser information between the identified DS0 and the identified ATMvirtual connection. Acknowledgments that the assignments have beenimplemented may be sent back to CCM 250 if desired.

In operation, calls are processed as follows. Signaling messages forcalls arrive on link 290 and are routed by STP 260 to CCM 250. Accessconnections are typically seized contemporaneously with the signaling.All of these connections are represented by connection 280. DS0interface 210 would convert the traffic on connection 280 into the DS0format and provide the DS0s to AAL 220 over connection 281.

The signaling received by CCM 250 would identify the access connectionsfor the calls (i.e. the particular DS0s on connection 280), and containcall information, such as a dialed number. CCM 250 would process thesignaling and select connections for the call. Since multiple virtualconnections are pre-provisioned from ATM interface 230 to the otherdestinations in the network, CCM 250 can select a virtual connection tothe destination. The selection process can be accomplished through tablelook-ups. For example, a table could be used to translate a portion ofthe dialed number into a VPI. The VCI would be selected based on theavailable VCIs in the selected VPI. The VPI/VCI combination wouldcorrespond to a unique virtual connection pre-provisioned from ATMinterface 230 to the appropriate network destination. The selectionsrepresent the DS0—virtual connection assignments that are provided toassignment 240 over link 292.

Assignment 240 accepts the DS0—virtual connection assignments andprovides them to AAL 220. When AAL 220 receives a particular assignment,it converts user information from the designated DS0 into cells thatidentify the designated VPI/VCI. The cells are provided to ATM interface230 over connection 282. ATM interface 230 accepts the cells and placesthem within the transport format for connection 283. The cells are thentransported over the selected virtual connection to the appropriatedestination.

Calls also exit the network through connection 280. In this case, CCMsat the origination points select the virtual connections to ATMinterface 230. The originating CCMs also send signaling messages to CCM250. The signaling messages identify the destinations for the calls andthe selected virtual connections. CCM 250 will have a list of availableaccess connections to the identified destinations. CCM 250 will selectthe access connections to the destination from the list. For example,the connection selected by CCM 250 could be a DS0 embedded within a DS3connected to a LEC. The virtual connections on connection 283 andselected access connections on connection 280 are provided to assignment240 over link 292. Assignment 240 provides these assignments to AAL 220.

ATM interface 230 will demux the cells arriving from connection 283 andprovide them to AAL 220. AAL 220 converts the user information in thecells into the DS0 format. AAL 220 make the conversion so that cellsfrom a particular virtual connection are provided to the assigned DS0 onconnection 281. DS0 interface will convert the DS0s from connection 281into the appropriate format, such as DS3, for connection 280. Thoseskilled in the art are aware of the techniques for muxing andtransporting DS0 signals.

From the above discussion, it can be seen that user information forcalls can flow from connection 280 to connection 283, and in the reversedirection from connection 283 to connection 280. DS0 interface 210 andATM interface 230 provide user information in their respective formatsto AAL 220. AAL 220 converts the user information between DS0 and ATMformats based on the assignments from assignment 240. CCM 250 can selectthe DS0—virtual connection assignments that drive the process.

The ATM Interworking Multiplexer

FIG. 3 shows one embodiment of the mux that is suitable for the presentinvention, but muxes that support the requirements of the invention arealso applicable. Shown are control interface 300, OC-3 interface 305,DS3 interface 310, DS1 interface 315, DS0 interface 320, digital signalprocessing (DSP) 325, AAL 330, and OC-12 interface 335.

OC-3 interface 305 accepts the OC-3 format and makes the conversion toDS3. DS3 interface 310 accepts the DS3 format and makes the conversionto DS1. DS3 interface 310 can accept DS3s from OC-3 interface 305 orfrom an external connection. DS1 interface 315 accepts the DS1 formatand makes the conversion to DS0. DS1 interface 315 can accept DS1s fromDS3 interface 310 or from an external connection. DS0 interface 320accepts the DS0 format and provides an interface to digital signalprocessing (DSP) 325.

DS0 interface 320 is coupled to DSP 325. DSP 325 is capable ofmanipulating the user information to improve transmission quality. DSPprocessing primarily entails echo cancellation, but could include otherfeatures as well. As is known, echo cancellation can be required forvoice calls. DSP 325 passes the DS0s through echo cancellers. These echocancellers must be disabled for calls that do not require echo control.Data calls do not require echo cancellation, and the CCM has the abilityto recognize data calls that require an echo canceller to be disabled.The CCM will send a control message through control interface 300 to DSP325 indicating the particular echo canceller that is to be disabled. TheCCM selects the echo canceller based on the CIC in the signaling itreceives from the user. After the data call, the CCM sends a messagethat causes the particular echo canceller to be enabled again forsubsequent voice calls. The above technique of applying echo control ispreferred, but other means of implementing echo control instructionsfrom the CCM are also applicable.

In addition to echo control, the CCM and the mux can work to provideother digital signal processing features on a call by call basis.Compression algorithms can be applied, either universally, or on a percall basis. The decibel level could be adjusted for calls form aparticular origin or to a particular destination, i.e. where a hearingimpaired person may reside. Encryption could be applied on acall-by-call basis based on various criteria like the origination numberor the destination number. Various DSP features could be associated withvarious call perameters and implemented by the CCM through DSP 325.

DSP 325 is connected to AAL 330. AAL 330 operates as described above foran AAL. DS0—virtual connection assignments from control interface 300are implemented by AAL 330 when converting between the DS0 and ATMformats.

Calls with a bit rate greater than 64 kbit/sec. are known as Nx64 calls.If desired, AAL 330 can be capable of accepting control messages throughcontrol interface 300 from the CCM for Nx64 calls. The CCM wouldinstruct AAL 330 to group the DS0s for the call.

The ATM Cross-connect System

FIG. 4 depicts virtual connections provided by the ATM cross connectsystem in a version of the invention, although numerous other techniquesfor providing virtual connections will be appreciated by one skilled inthe art, and the invention contemplates any such system. Shown arevirtual connections 410, 412, 414, 416, 418, and 420. These virtualconnections are shown interconnecting muxes A, B, and C throughcross-connects Y and Z. Virtual connections are provisioned in betweeneach mux. Each mux would have a virtual path to the cross-connect systemthat is designated for each possible destination mux. Virtual path ABcontains virtual connection 412 from mux A to mux B. For calls thatoriginate and terminate at the same mux, virtual connections 410, 416,and 420 are provisioned for that purpose. Virtual connections 414 and418 connect muxes A/C and B/C respectively. Alternate routes fordifferent virtual connections can be provisioned between the same twomuxes.

Within each virtual path are thousands of virtual channels (not shown).Virtual connections are provisioned by cross-connecting VPI/VCIcombinations at cross-connects Y and Z. If a call enters mux A and needsto terminate at mux B, the CCM will select virtual path AB. Theselection could be based on a translation of the dialed number. Withinvirtual path AB, the CCM would select the particular virtual channel.This selection could be based on available VCIs within the VPI. In thisway, pre-provisioned virtual connections can be selected on a call bycall basis.

Typically, calls will require a bi-directional voice connection. Forthis purpose, a virtual connection must transport user information inboth directions. The virtual connections can be provisioned so that themux at the terminating end may use the same VPI/VCI for cellstransported in the opposite direction. The terminating CCM could alsotranslate the originating VPI/VCI into another VPI/VCI provisioned inthe opposite direction and provide this VPI/VCI to the terminating mux.

Additionally, the number of active virtual connections in betweencross-connects can be tracked. Virtual path YZ connects cross-connects Yand Z. The capacity of virtual path YZ would be sized based on networkrequirements, but should it become overloaded, the CCMs can beprogrammed to select an alternate virtual path.

Operation within a Network

FIG. 5 depicts an embodiment of the invention with respect to a specifictelecommunications network scenario, although the invention is notlimited to this specific scenario. FIG. 5 shows telecommunicationssystem 500. Shown are user 510, user 512, user 514, user 516, STP 518,STP 520, STP 522, STP 524, mux 526, mux 528, mux 530, mux 532,call/connection manager (CCM) 534, CCM 536, CCM 538, CCM 540, ATMcross-connect 542, ATM cross-connect 544, and ATM cross-connect 546. Forclarity, the connections and signaling links are not numbered. All ofthese components are described, and the CCMs are also discussed below.

In operation, user 510 may forward an 800 call to system 500. User 510could be connected to mux 526 with a DS3 connection. The 800 call wouldoccupy a DS0 embedded in the DS3 connected to mux 526. User 510 wouldsend an SS7 Initial Address Message (IAM) through STP 518 to system 500.STP 520 would be configured to route the IAM to CCM 534. An IAM containsinformation such as the dialed number, the caller's number, and thecircuit identification code (CIC). The CIC identifies the DS0 used byuser 510 for the call.

CCM 534 would process the IAM and identify that the call was an 800call. Either through its own database or by accessing a service controlpoint (SCP) (not shown), the CCM would translate the dialed number basedon the 800 subscriber's routing plan. For example, 800 calls from user510 may be routed to user 512 during business hours, to user 514 atnight, and to user 516 on weekends. If the call is placed from user 512on a weekend, the call would be routed to user 516. As such, CCM 534would select a pre-provisioned virtual connection from mux 526 throughATM cross-connect 542 and ATM cross-connect 544 to mux 530. CCM 534would send an IAM message to CCM 538 through STP 520 and STP 522. TheIAM would indicate that a call was being routed to user 516 and wouldidentify the selected virtual connection being used to reach mux 530.

Typically, mux 530 would be connected to user 516 with a DS3 connection.CCM 538 would select a DS0 embedded in the DS3 and would send an IAM touser 516 through STP 522 and STP 524. The CIC of the IAM would indicatethat a call was being routed to user 516 over the selected DS0. User 516would process the IAM and complete the call. When the call is answered,user 516 would transmit an answer message (ANM) through STP 524 back tosystem 500.

CCM 534 would also send a UDP/IP message to mux 526 instructing it toassemble the user information in the DS0 from user 510 into ATM cellswith a cell header identifying the selected virtual connection. CCM 538would send a UDP/IP message to mux 530 instructing it to dis-assembleATM cells from the selected virtual connection and output the userinformation to the selected DS0 to user 516. ATM cross-connect 542 wouldroute ATM cells from mux 526 to ATM cross-connect 544 based on the cellheader. Likewise, ATM cross-connect 544 would route these cells to mux530 based on the cell header. As such, user information for the callwould flow from user 510 to user 516 over the DS0 from user 510, thevirtual connection selected by CCM 534, and the DS0 to user 516 selectedby CCM 538. The muxes would implement the selections of the CCMs.

The call would require that a voice channel be available in bothdirections. As such, the DS0s and virtual connection would bebi-directional. Cut-through on the receive channel (from the user 516 tothe user 510) would occur after the address complete message (ACM) hadbeen received by system 500. Cut-through on the transmit channel (fromthe user 510 to the user 516) would occur after the answer message (ANM)had been received by system 500. This could be accomplished by notallowing mux 530 to release any cells for the call until the ANM hasbeen received by system 500.

If user 510 were to place the call at night, CCM 534 would determinethat user 514 was the destination. Accordingly a pre-provisioned virtualconnection from mux 526 through ATM cross-connect 542 and ATMcross-connect 546 to mux 528 would be selected for the call. CCM 536would select the DS0 to user 514.

If user 510 were to place the call during the day, CCM 534 woulddetermine that user 512 was the destination. Accordingly apre-provisioned virtual connection from mux 526 through ATMcross-connect 542 and back to mux 526 would be selected for the call.CCM 534 would also select the DS0 to user 512.

The Call/Connection Manager (CCM)

FIGS. 6-12 refer to a preferred embodiment of the signaling processor,also known as the CCM, but any processor which supports the requirementsstated for the invention would suffice. FIG. 6 depicts a signalingprocessor suitable for the invention. Signaling processor 610 wouldtypically be separate from the mux, but those skilled in the artappreciate that they could be housed together. Also, signaling processormay support a single mux or support multiple muxes.

Signaling processor 610 includes Message Transfer Part (MTP) level 1612, MTP level 2 615, and MTP level 3 620. MTP level 1 612 defines thephysical and electrical requirements for a signaling link. MTP level 2615 sits on top of level 1 and maintains reliable transport over asignaling link by monitoring status and performing error checks.Together, MTP levels 1-2 provide reliable transport over an individuallink. A device would need MTP level 1-2 functionality for each link ituses. MTP level 3 620 sits on top of level 2 and provides a routing andmanagement function for the signaling system at large. MTP level 3 620directs messages to the proper signaling link (actually to the MTP level2 for that link). MTP level 3 620 directs messages to applications usingthe MTP levels for access the signaling system. MTP level 3 620 also hasa management function which monitors the status of the signaling systemand can take appropriate measures to restore service through the system.MTP levels 1-3 correspond to layers 1-3 of the open systemsinterconnection basic reference model (OSIBRF). Both the MTP 1-3 and theOSIBRF are well known in the art

Also shown for signaling processor 610 are ethernet interface 635,platform handler 640, message handler 645, and data handler 650.Ethernet interface 635 is a standard ethernet bus supporting TCP/IPwhich transfers signaling messages from MTP level 3 to platform handler640. Also, if UDP/IP is used to communicate with the muxes, ethernetinterface 335 would accept the links to the muxes. Those skilled in theart will recognize other interfaces and protocols which could supportthese functions in accord with the invention.

In accord with this invention, the logic of the signaling interface(indicated by reference numerals 612, 615, 620, and 635) would beoperational to route select ISUP messages to platform handler 640.Technique for doing this have been discussed above. Preferably, an SS7interface to platform handler 640 could be constructed usingcommercially available SS7 software interface tools. An example of suchtools would be SS7 interface software provided by Trillium, Inc.

Platform handler 640 is a system which accepts ISUP and B-ISUP messagesfrom ethernet interface 635 and routes them to message handler 645.Preferably, platform handler 640 is configured to route messages to aparticular message handler processor based on the signaling linkselection (SLS) code in the message. Message handler 645 is a systemwhich exchanges signaling with platform handler 640 and controls theconnection and switching requirements for the calls. It can select andimplement services and initiate echo control. It also converts signalingbetween ISUP and B-ISUP. Data handler 650 is a set of logic coupled tomessage handler 645 which processes service requests and provides datato message handler 645. Data handler 650 also controls echo cancellersand generates billing records for the call.

In the discussions that follow, the term ISUP will include B-ISUP aswell. In operation, ISUP messages that meet the proper criteria arerouted by MTP and/or ATM interface 615, MTP level 3 620, and ethernetinterface 635 to platform handler 640. Platform handler 640 would routethe ISUP messages to message handler 645. Message handler 645 wouldprocess the ISUP information. This might include validation, screening,and determining if additional data is needed for call processing. If so,data handler 650 would be invoked and would provide message handler 645with the relevant data so message handler 645 could complete callprocessing. Message handler 645 would generate the appropriate ISUPmessage to implement the call and pass the signals to platform handler640 for subsequent transmission to the designated network elements.

The distribution of functional entities among message handler 645 anddata handler 650 are shown. These functional entities are well known inthe art. Message handler 645 includes at least the call control function(CCF) and the service switching function (SSF). The CCF establishes andreleases call connections, and the SSF recognizes triggers during callprocessing by the CCF and provides an interface between the CCF and theservice control function (SCF). The SCF identifies services and obtainsdata for the service. In some embodiments, message handler 645 caninclude the SCF and the service data function (SDF). The SDF providesservice data in real time to the SCF. Taken together, message handler645 is able to at least control connections and recognize triggers. Insome embodiments, message handler 645 can also identify services, obtaindata for the services, and generate the signaling required to implementthe services. Message handler 645 can provide signaling interworking(i.e. ISUP to B-ISUP), connection control, service selection and serviceimplementation in a logically integrated package that interfaces withthe network through conventional means.

Data handler 650 includes at least the SCF and the SDF. In someembodiments, message handler 645 and data handler 650 both include theSCF and the SDF and services are partitioned among the functionalentities. Two other functions are shown in data handler that are notstandardized functional entities. Accounting generates a billing recordand echo handles the echo cancellers. Typically, an echo canceller isdisabled for a data call and enabled after the data call for use onsubsequent voice calls, however, other techniques are applicable.

In operation, the CCF would perform basic call processing until the SSFrecognized a trigger and invoked the SCF. The SCF would identify theservice associated with the trigger. The SCF would access data from theSDF in order to implement the service. The SCF would process the datafrom the SDF and provide the data to the CCF through the SSF. The CCFwould then set-up the connections through conventional signaling toservice switching points (SSPs). The SSPs are connected to thecommunications path and make the connections. Typically, an SSP is aswitch. Also, echo cancellers may be controlled for the call, and abilling record could be generated for the call.

Those skilled in the art are aware of various hardware components whichcan support the requirements of the invention. For example, the platformhandler, message handler, and data handler could each reside on aseparate SPARC station 20.

The Platform Handler

FIG. 7 shows a possible version of the platform handler. Platformhandler 710 is shown. Platform handler 710 includes STP handler 712,supervisor 714, and CCM handler 716. Platform handler 710 transmits andreceives ISUP messages to/from the signaling interface (referencenumerals 312, 315, 320, and 335). STP handler 712 would provide theethernet—TCP/IP interface. STP handler 712 has a process to buffer anddis-assemble the incoming packets to the CCM, and buffer and assembleoutgoing packets. STP handler 712 could also check the messages forbasic flaws. Any technique for transfer of signaling messages toplatform handler 710 is contemplated by the invention.

Supervisor 714 is responsible for managing and monitoring CCMactivities. Among these are CCM start-up and shut-down, log-in andlog-off of various CCM modules, handling administrative messages (i.e.error, warning, status, etc.) from the CCM modules, and handlingmessages from network operations such as queries, configurationinstructions, and data updates. The connection to network operations isthe man machine interface which allows the CCM to be controlled andmonitored by either a remote or a local operator. Supervisor 714 has aprocess which retrieves configuration data from internal tables toinitialize and configure the CCM. The CCM modules also have internaltables which are used in conjunction with this procedure. Supervisor 714also communicates internally with STP handler 712 and CCM handler 716.

CCM handler 716 exchanges ISUP information with STP handler 712. CCMhandler 716 also exchanges ISUP messages and CCM supervisory messageswith the message handler. The connection between CCM handler 716 and themessage handler could be an ethernet LAN transporting these messagesencapsulated in TCP/IP packets, but other methods are known. CCM handler716 would provide the ethernet—TCP/IP interface. CCM handler 716 has aprocess to buffer and dis-assemble the incoming packets from the messagehandler, and buffer and assemble outgoing packets to the messagehandler. CCM handler 716 could also check the messages for basic flaws.

Internally, platform handler 710 is equipped with bi-directionalchannels which exchange information among STP handler 712, supervisor714, and CCM handler 716. The channels between STP handler 712, CCMhandler 715, and supervisor 712 carry supervisory and administrativeinformation. The channel between STP handler 712 and CCM handler 716carries ISUP message information.

Platform handler 710 accepts, disassembles, and buffers ISUP messagesreceived from the network. It can perform basic checks on the messagesbefore transferring them to the message handler. Should more than onemessage handler be connected to platform handler 710, the ISUP messagescould be allocated to the message handlers based on the SLS of theparticular ISUP message. CCM handler 716 accepts routing instructionsfrom the message handler for routing certain ISUP messages to selectprocesses of the message handler. Platform handler 710 also providessupervision and a man/machine interface for the CCM.

The Message Handler

FIG. 8 depicts a version of the message handler. Message handler 820 isshown and includes call center 821, origination manager 822, terminationmanager 823, detection point manager 828, feature manager 824, auxiliarymanager 825, switching manager 826, and local resource 827. A primaryfunction of message handler 820 is to process ISUP messages.

Call center 821 is the process which receives call set-up messages fromthe platform handler. ISUP call set-up is initiated with the IAM. Whencall center 821 receives an IAM, it creates an instance of anorigination manager process with data defined by the information in theIAM. Origination manager 822 represents any of the origination managerprocesses spawned by call center 821. The CCM handler is instructed ofthe new instance so that subsequent ISUP messages related to that callcan be transferred directly to the appropriate instance of originationmanager 822 by the platform handler.

Origination manager 822 sets up a memory block called an originatingcall control block. The call control block provides a repository forinformation specific to a call. For example, the originating callcontrol block could identify the following: the call control block, theorigination manager, the message handler, the originating LEC, the LECtrunk circuit (CIC), the ATM virtual circuit, the ATM virtual path, thecaller's number, the dialed number, the translated dialed number, theoriginating line information, the ANI service class, the selected route,the number of the selected route, the SLS, the OPC, the DPC, the serviceindicator (SIO), echo cancellation status, reason of release, callstatus, and pointers to adjacent call control blocks. In addition, thecall control block would also contain the various times that signalingmessages are received, such the address complete message (ACM), theanswer message (ANM), the suspend message (SUS), the resume message(RES), and the release message (REL). Those skilled in the art would beaware of other pertinent data to include.

Origination manager 822 executes call processing in accordance with theBasic Call State Model (BCSM) recommended by the InternationalTelecommunications Union (ITU), but with some notable exceptions.Origination manager 822 processes the IAM through each point in call(PIC) until a detection point (DP) is encountered. When a detectionpoint is encountered, a message is sent to detection point manager 828and processing is suspended at origination manager 822 until detectionpoint manager 828 responds. An example of a detection point fororigination manager 822 would be to authorize an origination attempt.

Detection point manager 828 accepts messages from originating manager822 caused by a detection point encountered during call processing.Detection point manager 828 will identify whether or not the detectionpoint is armed. An armed detection point has specific criteria which canaffect call processing if met. If the detection point is not armed,detection point manager 828 will send a continue signal back toorigination manager 822. A continue message instructs originationmanager 822 to continue call processing to the next detection point. Ifthe detection point is armed, detection point manager 828 will takeaction to see if the detection point criteria are met. If detectionpoint manager 828 requires assistance to process the armed detectionpoint, it will send a message to feature manager 824.

Feature manager 824 would accept messages from detection point manager828 and either forward the a message to auxiliary manager 825 or toswitching manager 826. Particular feature messages would be routed toauxiliary manager 825 which will process these call features. These aretypically non-IN features, such as echo control or POTS billing. Otherfeature messages would be routed to switching manager 826. These aretypically IN features. Examples of IN features are 800 numbertranslation or a terminal mobility number translation. Feature manager824 will pass information back to detection point manager 828 (then toorigination manager 822) when it is received back from auxiliary manager825 or switching manager 826.

Switching manager 826 which will determine if the request will behandled by local resource 827 or by the data handler. Local resource 827will be structured to provide data more efficiently stored at messagehandler 820. Examples of such data include: an automatic numberidentification (ANI) validation table which checks the caller's number,a dialed number translation table to translate POTS numbers into arouting instructions, or N00 translation tables to translate select 800numbers into routing instructions. Examples of a routing instructionyielded by the tables would be a particular access connection or avirtual connection. An example of data in the data handler would bevirtual private network (VPN) routing tables or complex 800 routingplans.

Typically, originating manager 822 will execute through the pertinentpoints in call to a point indicating that set up is authorized. At thispoint, origination manager 822 will instruct call center 821 to createan instance of a termination manager. Termination manager 823 representsany of these termination managers. Origination manager 822 will alsotransfer IAM information to termination manager 823. Termination manager823 sets up a memory block called a terminating call control block. Thecall control block provides a repository for information specific to acall and is similar in composition to the originating call controlblock.

Termination manager 823 also operates in accord with the BCSM of theITU, but also with some exceptions. Termination manager 823 continuesprocessing for the call through its own points in call until detectionpoints are encountered. When a detection point is encountered, a messageis sent to detection point manager 828 and processing is suspended attermination manager 823 until detection point manager 828 responds. Anexample of detection point for termination manager 822 would be toauthorize termination which would entail authorizing the call as set-upby origination manager 822. Messages from termination manager 823 todetection point manager 828 are handled as discussed above for messagesfrom originating manager 822. When processing by termination manager 823is complete, it will produce a signaling message to transmit throughplatform handler 410 to the appropriate multiplexers, and possibly tothe users.

Message handler 820 communicates with the data handler using a datatransfer protocol. Examples include UDP/IP, or the Intelligent NetworkApplications Protocol (INAP) which is contained within the componentsublayer of Transaction Capabilities Application Part (TCAP).

The Data Handler

FIG. 9 shows a version of the data handler. Data handler 930 is shown.Data handler 930 includes service control center 931, service selection932, service logic center 933, feature process 934, service data center935, service data manager 936, echo control 937, and accounting 938.Data handler 930 receives service request messages from the messagehandler. These messages result from an armed detection points triggeringthe message handler to invoke data handler 930. The messages also resultfrom features implemented through the auxiliary manager. Service controlcenter 931, service logic center 933, and service data center 935 arestatic processes created at start-up. Service control center 931 createsinstances of service selection managers on a call by call basis. Servicecontrol center 931 notifies the Switching manager to route subsequentservice request messages for that call to the appropriate serviceselection manager. Service selection manager 932 represents any of theservice selection managers created by service control center 931.

Service selection manager 932 executes the service portion of the callprocessing. Service selection manager 932 identifies the variousservices associated with each message and implements the service throughmessages to service logic center 933. Service logic center 933 acceptsmessages from service selection 932 and creates instances of the featureprocesses required for the identified services. Examples of featureprocesses are N00, messaging, personal/terminal mobility, and virtualprivate network (VPN). Feature processes are service logic programswhich implement the required services for a call. Feature process 934represents any of the feature processes created by service logic center933. Feature process 934 accesses the network resources and datarequired to implement the service. This would entail executing serviceindependent blocks (SIBs). A SIB is a set of functions. An example of afunction would be to retrieve the called number from a signalingmessage. SIBs are combined to build a service. An example of a SIB istranslating a called number.

Those skilled in the art are familiar with the above services, althoughthey have never been implemented by a system such as the presentinvention. N00 services are services such as 800, 900, or 500 calling inwhich the dialed number is used to access call processing and billinglogic defined by the subscriber to the service. Messaging entailsconnecting the caller to a voice messaging service. For example, thereceipt of a release message (REL) with a cause of busy could be atrigger recognized by the message handler. In response, the data handlerwould create an instance of the messaging feature process and determinedif a call placed to a particular dialed number would require the voicemessaging platform. If so, the CCM would instruct an SSP to connect thecaller to the voice message platform. Personal/Terminal mobilityincludes recognizing that the dialed number has mobility that requires adatabase look-up to determine the current number. The database isupdated when the called party changes locations. VPN is a privatedialing plan. It is used for calls from particular dedicated lines, fromparticular calling numbers (ANIs), or to particular dialed numbers.Calls are routed as defined for the particular plan.

In the execution of the SIB to provide the service, feature process 934would invoke service data center 935 to create an instance of servicedata manager 936. Service data manager 936 accesses the networkdatabases that provide the data required for the service. Access couldbe facilitated by TCAP messaging to an SCP. Service data manager 936represents any of the service managers created by service data center935. Once the data is retrieved, it is transferred back down to featureprocess 934 for further service implementation. When the featureprocesses for a call finish execution, service information is passedback down to the message handler and ultimately to the origination ortermination manager for the call.

After a release message on a call, billing requests will be forwarded toaccounting 938. Accounting 938 will use the call control block to createa billing record. The call control block would contain information fromthe ISUP messages for the call and from CCM processing. From the addresscomplete message (ACM), the call control block would include the routinglabel, CIC, message type, and cause indicators. From the answer message(ANM), the call control block would include the routing label, CIC,message type, and backward call indicators. From the initial addressmessage (IAM), the call control block would include the routing label,CIC, message type, forward call indicators, user service information,called party number, calling party number, carrier identification,carrier selection information, charge number, generic address,origination line information, original called number, and redirectingnumber. From the release message (REL), the call control block wouldinclude the routing label, CIC, message type, and cause indicators. Fromthe suspend message (SUS) or the pass along message (PAM), the callcontrol block would include the routing label, CIC, and message type.Those skilled in the art are familiar with other pertinent informationfor a billing record and appreciate that some of this information couldbe deleted.

For POTS calls, the billing request will come from the origination andtermination managers through the auxiliary manager. For IN calls, therequest will come from service selection 932. Accounting 938 willgenerate a billing record from the call control blocks. The billingrecord will be forwarded to a billing system over a billing interface.An example of such an interface is the I.E.E.E. 802.3 FTAM protocol.

At some point during call set-up, the origination manager, terminationmanager or even the detection point process will check the user serviceinformation data and originating line information to assess the need forecho control. If the call is a data call, a message is sent to datahandler 930. Specifically, the message is routed through the auxiliarymanager to the echo control manager 937 in data handler 930. Based onthe CIC, echo control manager 937 can select which echo canceller andDS0 circuit needs to be disabled. A message will be generated to thateffect and transmitted over a standard data link to the pertinent echocanceller or echo control system. As described above, echo control canbe implemented by the multiplexer. Once a release (REL) message isreceived for the call, the echo canceller is re-enabled. On a typicalcall, this procedure will occur twice. Once for an echo canceller on theaccess side, and again for an echo canceller on the terminating side.The CCM that handles the IAM for a particular call segment will controlthe particular echo cancellers for the segment.

IAM Call Processing

Prior to a description of IAM processing, a brief description of SS7message is given. SS7 messaging is well known in the art. SS7 ISUPmessages contain numerous fields of information. Each message will havea routing label containing a destination point code (DPC), anorigination point code (OPC), and a signaling link selection (SLS) whichare used primarily for routing the message. Each message contains acircuit identification code (CIC) which identifies the circuit to whichthe message relates. Each message contains the message type which isused to recognize the message. ISUP messages also contain mandatoryparts filled with fixed length data and variable length data, inaddition to a part available for optional data. These parts vary frommessage type to message type depending on the information needed.

The initial address message (IAM) initiates the call and contains callset-up information, such as the dialed number. IAMs are transferred inthe calling direction to set up the call. During this process, TCAPmessages may be sent to access remote data and processing. When the IAMshave reached the final network element, an address complete message(ACM) is sent in the backward direction to indicate that the requiredinformation is available and the called party can be alerted. If thecalled party answers, an answer message (ANM) is sent in the backwarddirection indicating that the call/connection will be used. If thecalling party hangs up, a release message (REL) is sent to indicate theconnection is not being used and can be torn down. If the called partyhangs up, a suspend message (SUS) is sent and if the called partyreconnects, a resume (RES) message keeps the line open, but if their isno re-connection, a release message (REL) is sent. When the connectionsare free, release complete messages (RLC) are sent to indicate that theconnection can be re-used for another call. Those skilled in the art areaware of other ISUP messages, however, these are the primary ones to beconsidered. As can be seen, the IAM is the message that sets-up thecall.

In the preferred embodiment, call processing deviates from the basiccall model recommended by the ITU, although strict adherence to themodel could be achieved in other embodiments. FIGS. 10-12 depicts thepreferred call processing. Referring first to FIG. 10, When the IAM fora call is received at 1005, the call center creates an instance of anorigination manager at 1010.

The origination manager begins call processing by sending an authorizemessage to the detection point manager. Detection point manager checksIAM information, including the dialed number, the CIC, and theoriginating line information, to perform service discrimination at 1015.This is done to determine if the service requested requires validationat 1020. Current call processing systems and the BCSM of the ITU bothvalidate the call before performing service discrimination. In asignificant advance over the prior art, the preferred embodimentdeviates from known call processing methods by looking at the IAMinformation prior to validation to determine if validation is evenrequired. For example, the calling party may not pay the bill for acall. The called party pays the bill on 800 calls and validation can beunnecessary. If validation is not required at 1020, call processingproceeds directly to B. Advantageously, this avoids unnecessary look-upsin validation tables for a significant percentage of calls.

If validation is required at 1020, a validation table is checked at1025. Validation checks to see if a call should be allowed and focuseson potential billing problems for the call. For example, calls from ANIsthat are delinquent on payments pose problems for billing and may not bevalidated. Validation would entail messaging from the detection pointmanager through the feature manager and the switching manager to thelocal resource to access the tables. The table may list authorized ANIs,unauthorized ANIs, or both. If the call is not authorized at 1030,treatment (i.e. route to an operator or message) is given to the call at1035.

If the call is authorized at 1030, the services identified at 1015 arechecked at 1040 to determine if the call can be routed. This wouldtypically occur for POTS calls. If no additional services are requiredat 1040, the dialed number is translated into a route instruction at1045. The route instruction could be a particular virtual connectionand/or access connections. The processing then proceeds to A. Ifadditional services are required at 1040, processing proceeds to B.

FIG. 11 picks up processing at B after a route has been selected. Atermination manager is created at 1105. The termination manager isresponsible for processing in accordance with the terminating BCSM ofthe ITU. However, in some embodiments, the processing can exhibit somedeviation. For example, detection points such as select facility andvalidate call may be skipped.

The bearer capability is analyzed at 1110 to determine if the call is adata call at 1115. This analysis could occur elsewhere in the callprocessing (i.e. by the origination manager after the route isselected.) If a data call is found at 1115, an echo control message issent to the data handler at 1120. Echo control instructions are createdat 1125. The echo control instructions identify the connection for thecall which requires echo control. The message could be sent to the echocontrol system over a conventional data link from the CCM to the echocontrol system. If, the echo control is implemented in the multiplexers,the echo control message could be included with the route instructionmessage.

If the call is not a data call at 1115 or after echo control processingat 1125, a signaling message is created at 1135. The new signalingmessage identifies the access connections and virtual connection for thecall. The new signaling message can also contain echo controlinstructions. The new signaling message is sent to the platform handlerat 1140.

FIG. 12 picks up the processing at B. At this point, several things areknown about the call concerning authorization and service requirements.The call information is then analyzed at 1205 as required to applyservices to the call. If the data handler is not required at 1210, theservice is implemented and the route is selected at 1215. This may occurif a service can be directly implemented by the origination manager orthrough the local resource. For example, particular 800 translations ordialed number service profiles (i.e. call forwarding) can be stored inthe local resource. In this case, route selection would be performed bythe local resource after the information is analyzed to identify thecorrect entry to a local resource database. When the local resource isused, the messages must be routed from the detection point processorthrough the feature manager and switching manager to the local resource.

If the data handler is required for the call at 1210, a message is sentto the data handler at 1220. The messaging typically flows from thedetection point processor to the feature manager and switching managerto the data handler. Upon receipt of the message at the data handler,the service control center creates an instance of the service selectionprocess at 1225. The service selection process analyzes the message fromthe detection point processor and selects the feature processes for thecall at 1230. For example, a call may be placed from a caller in avirtual private network (VPN) to a PCS number. In this case, both a VPNfeature process and a PCS feature process would be created.

Each feature process would determine if data was required at 1240. Forexample, a personal mobility feature process would need to access adatabase to locate the called party's current telephone number. If datais required at 1240, the service data center creates a service datamanager at 1245. The data manager manages the data session and accessesthe appropriate database at 1250. After the data is collected (or noneis needed), the service is implemented by the feature process at 1255.For some features, i.e. 800 service, this may include route selection.The results of the feature process analysis are returned to theorigination manager to assimilate. If the feature process does notprovide the route, the origination manager must select the route usingthe local resource or another feature process.

The IAM itself contains numerous fields of information. The followingtable describes the elements of an IAM with regard to the informationcontent and call processing.

TABLE 1 Initial Address Message Parameter Field Name Description ROUTINGLABEL Service Indicator Set at 0101-ISDN user part Priority 0 or 1 basedon destination Network ID 10 for national network or set based oninternational trunk group Destination Point Code Destination of IAMOriginating Point Code Origination of IAM Signaling Link Connection Linkused for messages (same for all messages for the call) Circuit ID CodeCircuit used for the call between OPC and DPC in the IAM Message Type0000 or 0001 for IAM NATURE OF CONNECTION INDICATORS Satellite IndicatorIncrement for each satellite used Continuity Check Indicator 00 - nocheck 01 - set up check and start COT timer 10 - start timer for COTmessage. Echo Suppresser Indicator Indicates if echo control alreadyimplemented or is set if echo control is implemented FORWARD CALLINDICATORS National/International Call Indicator 0 for domestic 1 forinternational End to End Method Indicator Pass any informationInterworking Indicator Pass any information IAM Segmentation Indicator 0for POTS ISDN User Part Indicator Pass any information ISDN PreferenceIndicator Pass any information and default to 00 ISDN Access IndicatorPass any information SCCP Method Indicator 00 CALLING PARTIES CATEGORYCalling Party Category 00000000 for unknown 00001010 for ordinary caller00001101 for test call USER SERVICE INFORMATION Information TransferCapability Pass any information unless destination requires particularsettings, but always pass ISDN “unrestricted digital information” CodingStandard 00 Extension 1 Information Transfer Rate Pass any information(will be 10000 for POTS) Transfer Mode Set at 00 for 64 kbit/secExtension 1 User Layer Protocol Identification Set based on rateadaption, typically 0100010 for user information layer 1 Extension 1 fornormal calls 0 for rate adaption Rate Nothing for user information layer1, but 0111 for other rate adaption Extension 1 CALLED PARTY NUMBERNature of Address Indicator Identifies the type of call: 0000001 -original NPA or 950 call 0000011 - 1+ call 0000100 - direct dialinternational call 1110001 - operator call 1110010 - operator default1110011 - international operator call 1110100 - long distance operatorcall 1110101 - cut through call 1110110 - 950, hotel/motel, or non equalaccess call 1110111 - test call Odd/Even number of digits in a callednumber Numbering Plan 000 - default 001 - for ISDN 101 - private DigitsField number of the called party ACCESS TRANSPORT Access TransportElements pass any information CALLING PARTY NUMBER Nature of AddressIndicator Indicates the type of calling party address, unique numberscan be used for billing, but the charge number is used for non-uniquenumbers: 0000000 - unknown 0000001 - unique caller number 0000011 -unique national number 0000100 - unique international number 1110001 -non-unique caller number 1110011 - non-unique national number 1110100 -non-unique international number 1110111 - test call Odd/Even Number ofdigits in the calling number Screening Not applicable PresentationAllowed/Restricted Pass any information for POTS, but restrict for N00calls that are not allowed Numbering Plan 000 - default 001 - ISDN 101 -private Digits Field Number of the calling party CARRIER IDENTIFICATIONNetwork Identification Plan Number of digits in identification code forthe requested carrier Type of Network Identification Identifies thenetwork numbering plan for the call - 010 for POTS call from LEC DigitOne First digit in carrier identification code Digit Two Second digit incarrier identification code Digit Three Third digit in carrieridentification code Digit Four or Null Fourth digit in carrieridentification code (if there are four digits) CARRIER SELECTIONINFORMATION Carrier Selection Indicator Indicates whether the carrieridentification code was presubscribed or input CHARGE NUMBER Nature ofAddress Indicator This information may be used for billing. 00000001 -caller number 00000010 - no ANI, route to operator 00000011 - caller'snational number 00000101 - route if 800, or route to operator 0000110 -no ANI 0000111 - route if 800 or route to operator Odd/Even Number ofdigits in calling number Numbering Plan Pass any information DigitsField The number of calling party GENERIC ADDRESS Nature of AddressIndicator Pass any information Odd/Even Pass any information ScreeningPass any information Presentation Allowed/Restricted Pass anyinformation Numbering Plan Pass any information Digits Field Pass anyinformation ORIGINATING LINE INFORMATION Originating Line InformationIdentifies particular types of calls, for example: 00000000 - normalcall 00000111 - call from a restricted phone 00111111 - call from acellular roamer ORIGINAL CALLED NUMBER Nature of address Indicator Passany information Odd/Even Pass any information Screening Pass anyinformation Presentation Allowed/Restricted Pass any informationNumbering Plan Pass any information Digits Field Pass any informationREDIRECTING NUMBER Nature of Address Indicator Pass any informationOdd/Even Pass any information Screening Pass any informationPresentation Allowed/Restricted Pass any information Numbering Plan Passany information Digits Field Pass any information REDIRECTIONINFORMATION Redirection Indicator Pass any information OriginalRedirecting Reason Pass any information Redirection Counter Pass anyinformation Redirection Reason Pass any information SERVICE CODE ServiceCode Pass any information TRANSIT NETWORK SELECTION NetworkIdentification Plan Identifies the number of digits in the carrieridentification code (3 or 4) Type of Network Identification Type ofnetwork identification for transit network parameter Digits 1, 2, 3, 4Carrier identification code of the international transit carrier CircuitCode Indicates how the call was dialed: 0001 - international call, nooperator requested 0010 - international call, operator requested HOPCOUNTER Hop Counter limits the number of times an IAM may transferthrough a signaling point. If the count reaches the limit, release thecall

Subsequent ISUP Message Processing

The processing of the IAM is discussed above. Those skilled in the artare will appreciate how other SS7 messages can be incorporated into theprocessing of the present invention. For example, the time an addresscomplete message (ACM) is received is recorded in the call control blockfor billing and maintenance. Triggers can also be based on receipt ofsubsequent messages, such as the ACM. The process for the answer message(ANM) is much the same.

Cut-through is the time point at which the users are able to passinformation along the call connection from end to end. Messages from theCCM to the appropriate network elements are required to allow forcut-through of the call. Typically, call connections include both atransmit path from the caller and a receive path to the caller, and cutthrough is allowed on the receive path after the ACM is received and onthe transmit path after the ANM is received.

Upon receipt of a release (REL) message, the CCM will write a time forthe message to the call control block and check for triggers uponrelease (such as call re-originate). Additionally, any disabled echocanceller will be re-enabled, and the call control block will be used tocreate a billing record. Upon the receipt of a release complete message(RLC), the CCM will transmit messages directing tear down of the callpath. It will clear its call specific processes and reuse the callconnections for subsequent calls.

Additionally, suspend messages (SUS) and pass along messages (PAM) maybe processed by the CCM. A suspend message (SUS) indicates that thecalled party has disconnected and a REL will follow if the called partydoes not re-connect with a specified time. A PAM is simply a messagebetween signaling points and can contain a variety of information and beused for a variety of purposes.

The invention allows switching over an ATM fabric on a call by callbasis. This allows efficient high capacity virtual connections to beexploited. Advantageously, the invention does not require signalingcapability in an ATM switch. The invention does not require callprocessing capability in an ATM switch. This enables networks toimplement ATM switching without these sophisticated ATM switches thatsupport high volumes of calls. It also avoids the cost of theseswitches. The invention fully supports voice traffic and non-voicetraffic. The invention supports services, such as N00, VPN,personal/terminal mobility, and voice messaging without requiring theservice capability in an ATM switch. Relying on ATM cross-connects isadvantageous because ATM cross-connects are farther advanced than ATMswitches, and the cross-connects require less administrative support.

Those skilled in the art will appreciate that variations from thespecific embodiments disclosed above are contemplated by the invention.The invention should not be restricted to the above embodiments, butshould be measured by the following claims.

What is claimed is:
 1. A method of operating a communication signalingprocessor, the method comprising: receiving a signaling message for avoice call to a called party; processing the signaling message with avirtual private network plan to transfer a query to a database that isupdated when the called party changes locations; receiving a responsefrom the database; processing the response to select an identifier forpacket headers of a packetized voice communication to route the voicecall to the called party; and transferring an Internet Protocol messageindicating the selected identifier.
 2. The method of claim 1 wherein thesignaling message comprises a signaling system seven message.
 3. Themethod of claim 1 wherein the signaling message comprises an initialaddress message.
 4. The method of claim 1 wherein the identifiercomprises an asynchronous transfer mode virtual path identifier.
 5. Themethod of claim 1 wherein the identifier comprises an asynchronoustransfer mode virtual channel identifier.
 6. The method of claim 1wherein the header comprises asynchronous transfer mode cell header. 7.The method of claim 1 wherein processing the signaling message with thevirtual private network plan comprises processing the signaling messagewith the virtual private network plan in response to a caller number forthe voice call.
 8. The method of claim 1 wherein processing thesignaling message with the virtual private network plan comprisesprocessing the signaling message with the virtual private network planin response to a called number for the voice call.
 9. The method ofclaim 1 wherein processing the signaling message with the virtualprivate network plan comprises processing the signaling message with thevirtual private network plan in response to an incoming line for thevoice call.
 10. The method of claim 1 further comprising: receivinganother signaling message indicating that the called party is busy; andprocessing the other signaling message to select another identifier forthe packet headers of the packetized voice communication for the voicecall to route the voice call to a voice messaging platform.
 11. Themethod of claim 10 wherein the other identifier comprises anasynchronous transfer mode virtual path identifier.
 12. The method ofclaim 10 wherein the other identifier comprises an asynchronous transfermode virtual channel identifier.
 13. The method of claim 10 wherein theheader comprises asynchronous transfer mode cell header.
 14. A method ofoperating a communication signaling processor, the method comprising:receiving a signaling message for a voice call to a called party;processing the signaling message to transfer a query to a database thatis updated when the called party changes locations; receiving a responsefrom the database; processing the response to select an identifier forpacket headers of a packetized voice communication to route the voicecall to the called party; transferring an Internet Protocol messageindicating the selected identifier; receiving another signaling messageindicating that the called party is busy; and processing the othersignaling message to select another identifier for the packet headers ofthe packetized voice communication to route the voice call to a voicemessaging platform.
 15. The method of claim 14 wherein the othersignaling message comprises a signaling system seven message.
 16. Themethod of claim 14 wherein the other signaling message comprises arelease message.
 17. The method of claim 14 wherein the other identifiercomprises an asynchronous transfer mode virtual path identifier.
 18. Themethod of claim 14 wherein the other identifier comprises anasynchronous transfer mode virtual channel identifier.
 19. The method ofclaim 14 wherein the header comprises asynchronous transfer mode cellheader.